Release 10.1A: OpenEdge Data Management:
DataServer for ODBC
FIND statements
The DataServer fully supports the
FINDFIRST,CURRENT,LAST,PREV, andNEXTstatements for ODBC data-source tables that have unique indexes. If a table has no unique index, only theFINDFIRSTandFINDNEXTstatements are available for that table. The following section provides additional information about specificFINDstatements.FIND PREV and FIND LAST statements
Applications that use the
FINDPREVorFINDLASTstatements work on ODBC data-source tables in a manner consistent with OpenEdge. The only exception occurs when theFINDPREVorFINDLASTstatement fails. In the OpenEdge case, the cursor is located after the last record that was scanned. In the data-source case, the cursor behaves as if the failedFINDhad never occurred. To support these statements, a data-source table must include support for the ProgressROWIDfunction (through either aPROGRESS_RECIDcolumn or an indexed NUMBER column with unique values). See the "ROWID function" section for more information.For example, the procedure find.p accesses OpenEdge databases and ODBC data sources using the same
FINDandFIND PREVstatements in each case:
When you run
find.pwith an OpenEdge table and a data-source table, you get these results (assuming that the database has records for customer numbers 1 through 4):
![]()
If the
FINDPREVstatement fails, the cursor remains located aftercustomer.cust-num3 in the OpenEdge table, which was the last record scanned. In the data-source table, the cursor is positioned atcust-num2. Failed finds do not affect cursor position in data-source tables.FIND NEXT statement
The
FINDNEXTstatement can generate different results when you use it to access an ODBC data source through the DataServer than when you use it to access an OpenEdge database. When accessing an ODBC data source:
|
Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |